Repository navigation
Support turso:// URLs in the Sequel adapter - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Turso Cloud supplies
turso://database URLs, but the adapter currently treats that scheme as a local filename when passed asdatabase:and cannot load it throughSequel.connect(url). This change recognizes the scheme and normalizes it tohttps://for the existing native driver.turso://throughdatabase:,url:, and the direct Sequel URL form, including replica configuration.The
turso_libsql0.2.0 pin remains unchanged because 0.2.1 contains native credential debug logging.Validation on Apple Silicon macOS / Ruby 4.0.5 / Sequel 5.109.0:
bundle exec rake check: syntax/warning and visibility checks passed; 42 tests, 206 assertions, no failures or errors.test/remote.rbagainst a real hosted Turso database using aturso://URL: 5 tests, 24 assertions, no failures or errors. Covered authenticated HTTPS CRUD, bindings, Unicode/blobs, constraints, transactions/savepoints/rollback, reconnect persistence, schema metadata, prepared model operations, and returning writes. Temporary test tables were removed afterward.Embedded replication, credential rotation, and production load behavior remain unverified.